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!
Related
Over the past 12 hours I've had to pull the battery 3 times...
The phone was running fine all day (and generally is always very stable for the months I've had it). I put it down last night before I went to bed and when I picked it up again for some bedtime browsing the screen wouldn't come on. I pressed both the trackball (I have CM6 on it) and power button, nothing. I then plugged it in (I knew it was low, but not low enough to power off) and nothing, no light, nothing. I then got a touch scared. I pulled the battery, put it back in and it rebooted. It was fine for the rest of the night...
I plugged it in for the overnight, and when I woke up the light was still orange. The screen again wouldn't turn on. Battery pulled, it rebooted, and it was usable (full charge). I left the phone alone for about 20 mins (unplugged) and now it's back to being unable to turn on the screen.
- I've had CM6 final on it since soon after release with no issues
- I generally use Pershoot's kernels and I think (think) I updated to the latest .35 kernel yesterday. Again, I've never had an issue really in the past
- Updated TBA Pro, added the screen calibration apk, and removed quick office.apk via Root Explorer.
That's about it for "new" stuff I did yesterday.
Gonna put on Pershoots latest .34 kernel (I really don't think that's the issue) and see if that makes a difference (I always use the .35 kernels). I also wiped the dalvik cache. If that doesn't work, I'll remove the calibration app.
Any other opinions? Possible battery pooched? I charge it nightly, but other than that there hasn't been an issue. Certainly would be the first time I killed a battery in a phone...
tomedic said:
Over the past 12 hours I've had to pull the battery 3 times...
The phone was running fine all day (and generally is always very stable for the months I've had it). I put it down last night before I went to bed and when I picked it up again for some bedtime browsing the screen wouldn't come on. I pressed both the trackball (I have CM6 on it) and power button, nothing. I then plugged it in (I knew it was low, but not low enough to power off) and nothing, no light, nothing. I then got a touch scared. I pulled the battery, put it back in and it rebooted. It was fine for the rest of the night...
I plugged it in for the overnight, and when I woke up the light was still orange. The screen again wouldn't turn on. Battery pulled, it rebooted, and it was usable (full charge). I left the phone alone for about 20 mins (unplugged) and now it's back to being unable to turn on the screen.
- I've had CM6 final on it since soon after release with no issues
- I generally use Pershoot's kernels and I think (think) I updated to the latest .35 kernel yesterday. Again, I've never had an issue really in the past
- Updated TBA Pro, added the screen calibration apk, and removed quick office.apk via Root Explorer.
That's about it for "new" stuff I did yesterday.
Gonna put on Pershoots latest .34 kernel (I really don't think that's the issue) and see if that makes a difference (I always use the .35 kernels). I also wiped the dalvik cache. If that doesn't work, I'll remove the calibration app.
Any other opinions? Possible battery pooched? I charge it nightly, but other than that there hasn't been an issue. Certainly would be the first time I killed a battery in a phone...
Click to expand...
Click to collapse
That happened to me once when I installed one of IR's .35 kernel. I reverted to pershoot's and all was fine. (IR's new kernels are fine too)
ctbear said:
That happened to me once when I installed one of IR's .35 kernel. I reverted to pershoot's and all was fine. (IR's new kernels are fine too)
Click to expand...
Click to collapse
Ya, maybe... I put on the kernel in the morning though and all was fine all day. I installed his latest .34.7 kernel and wiped dalvik cache. So far so good...
Cheers, had the same issue and sofar this seems to have fixed it
My NC is installed CM7.0.3 in emmc mode. Every time when the battery reache around 31%, it will black out. No matter how i press the power key,it hasn't any reaction. Untill i plug on the USB charger, it'll power on to the system and charge the battery at 31%, and It work at seem to be normal.
Has anyone else experienced problems like these?
nope ive gone down 20 percent this has never happened to me.
wah67 said:
My NC is installed CM7.0.3 in emmc mode. Every time when the battery reache around 31%, it will black out. No matter how i press the power key,it hasn't any reaction. Untill i plug on the USB charger, it'll power on to the system and charge the battery at 31%, and It work at seem to be normal.
Has anyone else experienced problems like these?
Click to expand...
Click to collapse
Have you tried recalibrating the battery with the menu option in CMR? Need to charge to 100% before you do it though. It may be displaying a false %.
angomy said:
Have you tried recalibrating the battery with the menu option in CMR? Need to charge to 100% before you do it though. It may be displaying a false %.
Click to expand...
Click to collapse
Yeah, i have tried the battery calibration, the battery doctor, and wipe the battery status at recovery mode, also every time i have waited the battery to charge up to 100%, but nothing to change.
Mines does that. Around 12%. Screen turns right Barack up when plugged in though
Sent from my NookColor using XDA Premium App
I had the exact same problem as you. In the end I flashed back to the stock B&N 1.2 firmware, then left it plugged in overnight. Next day I used CWM to reset battery stats and wipe system/data/cache, before installing CM7. Attempted to drain the battery and it went all the way down to 0% =).
celyst said:
I had the exact same problem as you. In the end I flashed back to the stock B&N 1.2 firmware, then left it plugged in overnight. Next day I used CWM to reset battery stats and wipe system/data/cache, before installing CM7. Attempted to drain the battery and it went all the way down to 0% =).
Click to expand...
Click to collapse
I have the same problem except I'm running stock 1.2 unrooted. I have a CM7 build on a microSD that I use sometimes. How would you recommend I reset battery stats?
Mine has the problem but it started when I updated u-boot.bin to 1.2 for putting 2.6.32 kernel and Dal's CM7 on my NC.
First time it happened at 40% and before that battery % went up while off charger with 2.6.29 kernel.
With 2.6.32 kernel, it happened at 37%.
Put it on USB charger, it booted up fine. Will try to reset battery stats once fully charged. By the way, charger N is orange when CM battery % says 100%. Stats definitely are screwed up. Hope CWR battery reset will do the trick.
Same issue, stumped
My battery seems to die (screen blacks out) at 30 percent, sometimes 28 or 29%. Uptime prior to that happening is roughly 11 hours or so, with these stats before blinking off:
Battery status: Discharging
Power plug: unplugged
Battery level: 28
Battery scale: 100
Battery health: Good
Battery voltage: 3373 mV
Battery temperature: 36.9 C
Running Android 2.3.3
CM 7.0.3-encore
It didn't always do this, just recently in the past two days. I can't help but feel it's tied to an install, but the Netflix build.prop fix is the only one I can really remember being significant.
At 100% charged I've wiped the battery status in recovery, cleared cache (tried to wipe dalvik but got an error) and the nook still turned off at 30%. I recharged just enough to get the battery up to 31% and re-edited build.prop back to the original settings, rebooted, and waited for it to run down again. It died at 29%.
Desperately looking for ideas short of a reinstall of the mod...
lilgrass71 said:
Screen turns right Barack up when plugged in though
Click to expand...
Click to collapse
Nice spellcheck you have there!
im getting this power out thingy also
Its an issue associated with the 1.2 upgrade not cm7. I have same problem at about 25%.
Sent from my Nook Color running CM7 nightly 74.
ddgarcia05 said:
Its an issue associated with the 1.2 upgrade not cm7. I have same problem at about 25%.
Click to expand...
Click to collapse
If it is related to the 1.2 upgrade, what's confusing me is that my nook just recently started doing it a couple of days ago. Prior to that I could get a full discharge.
Overall I don't think the battery is bad, since I can get a full day of play with it with Wifi on most of the time and streaming about a 2 hours of video. But having 30% be the new zero is just weird.
ddgarcia05 said:
Its an issue associated with the 1.2 upgrade not cm7. I have same problem at about 25%.
Sent from my Nook Color running CM7 nightly 74.
Click to expand...
Click to collapse
B&N 1.2.0 ROM or the 1.2.0 u-boot stuff? Because I'd only believe this if you're saying it happens consistently on the 1.2.0 B&N ROM..
cymoze said:
My battery seems to die (screen blacks out) at 30 percent, sometimes 28 or 29%.
Click to expand...
Click to collapse
I don't have it blanking out until I get to about 10%. I wonder what the difference is... I am using a nootered nook and OC kernel.
just noticed this over the weekend. I was actually charging to reset the battery stats. judging from the other posts I can expect that not to help.
I don't recall itdoing it immediately after the 1.2 uboot but I'm now on the cyanogen 1.2 and its the same. worst part istheres no warning at all just blanks out.
Check this thread for more info, everyone is trying to find out why as well.
http://forum.xda-developers.com/showthread.php?p=14182742#post14182742
I Am Marino said:
Check this thread for more info, everyone is trying to find out why as well.
http://forum.xda-developers.com/showthread.php?p=14182742#post14182742
Click to expand...
Click to collapse
Thanks for the link. I wish I could contribute on that discussion but I am about 7 posts short. I am not using an overclocked kernel whatsoever, but my experience mirrors those listed there: death at under 3000 Mv, which for me occurs around the 30% battery level.
My stats are, to the best of my knowledge since I'm very much a noob, here:
PBD REPORT FORM
TEST CONFIGURATION:
BOOT DEVICE: eMMC
MLO: BN 1.2 stock
U-BOOT: ?
KERNEL: 2.6.29-omap1
OVERCLOCKED?: No
GOVERNOR: ONDEMAND
SYSTEM: CM7 7.0.3-encore
PBD: YES
TEST COUNT: 3x
TRIED REVERTING TO OLDER HC/CM7: NO
TRIED WIPING CACHE/DATA?: YES
DID IT WORK? NO
PREVIOUSLY INSTALLED:
_ Stock 1.1
X Stock 1.2
_ CM7 2.29 (any)
_ CM7 2.32 beta 3
One more "me too"... Happens to me around 25%... Have to plug back into the wall for second and then boot back up when it happens... Pretty scary if I were using this thing for any real work - luckily, it's just a play-thing for me to learn Android (got my eye on the new Asus tablets though!)...
This problem is happening to me as well. I
haven't updated to the 1.2 firmware and running CM 7.03. The screen will black out at 30%. Will wiping battery stats in CWR not help?
PBD REPORT FORM
TEST CONFIGURATION:
BOOT DEVICE: eMMC
MLO: BN 1.1 stock
U-BOOT: ?
KERNEL: 2.6.29-omap1
OVERCLOCKED?: Yes to 1.2GHz
GOVERNOR: INTERACTIVE
SYSTEM: CM7 7.0.3-encore
PBD: YES
TEST COUNT: 1x
TRIED REVERTING TO OLDER HC/CM7: NO
TRIED WIPING CACHE/DATA?: NO, wiped battery stats
DID IT WORK?
PREVIOUSLY INSTALLED:
x Stock 1.1
_ Stock 1.2
_ CM7 2.29 (any)
x CM7 2.32 beta 3 -- reverted back to CM 7.03
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
Heys Guys Im having an issue with my Captivate, its was working fine for the past week. It started giving me problems like battery temps too high, cant charge, had to charge it manually, removing battery & charging it all night. All this happened when im with stock rom latest with leaked 2.3.5
& i did unlock this with changing the 01 digit to 00 in efs file.
From the past 2 days im trying to install CM10,9, 10.1..... after installation it shuts down itself. Not able to use it.
Is there any way around to make this work. If pics are needed i can provide that too.
Thanks
No reply... :/
Some one should have had an issue.
vivek90 said:
Heys Guys Im having an issue with my Captivate, its was working fine for the past week. It started giving me problems like battery temps too high, cant charge, had to charge it manually, removing battery & charging it all night. All this happened when im with stock rom latest with leaked 2.3.5
& i did unlock this with changing the 01 digit to 00 in efs file.
From the past 2 days im trying to install CM10,9, 10.1..... after installation it shuts down itself. Not able to use it.
Is there any way around to make this work. If pics are needed i can provide that too.
Thanks
Click to expand...
Click to collapse
When/how does it happen?
What are the changes/mods you made?
Did you restore anything?
Did you try different kernel settings?
Did you try flashing a different kernel (like Semaphore?) or flashing a different ROM?
I could be asking more questions but really, I dunno what causes it, I can only guess. Also a search in the CM10.1 thread might give you an answer to your SoD <-- Should've been your first step*
BWolf56 said:
When/how does it happen?
What are the changes/mods you made?
Did you restore anything?
Did you try different kernel settings?
Did you try flashing a different kernel (like Semaphore?) or flashing a different ROM?
I could be asking more questions but really, I dunno what causes it, I can only guess. Also a search in the CM10.1 thread might give you an answer to your SoD <-- Should've been your first step*
Click to expand...
Click to collapse
It just happened, battery temp too high errors, thought flashing CM9 would solve this, was bored of Stock Gingerbread, flashed corn kernel & flashed cm9 rom. I did mod anything else. That all
vivek90 said:
It just happened, battery temp too high errors, thought flashing CM9 would solve this, was bored of Stock Gingerbread, flashed corn kernel & flashed cm9 rom. I did mod anything else. That all
Click to expand...
Click to collapse
Battery temp to high is a big problem. Did you overcloak? Have you running bunch of stuff at the same time?
When it shuts down, does it reboot by itself or you have to do it manually?
Sent from my SGH-I747 using xda app-developers app
Sounds like Battery health status does not equal healthy. That forces an immediate shutdown, whether due to temperature or excessive internal resistance. That's because once a Li ion battery reaches critical temperature, it combusts and destroys your phone, burns you and anything around it, etc.
GET ANOTHER BATTERY ASAP.
Stop trying to circumvent high temperature shut down.
.........
BWolf56 said:
Battery temp to high is a big problem. Did you overcloak? Have you running bunch of stuff at the same time?
When it shuts down, does it reboot by itself or you have to do it manually?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Recently i bought a new battery, original samsung make, it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high". No overclocking here, just used to call, receive & wifi hotspot. Currently i charge battery in a battery charger & use it in phone.
U pointed out something right, sometimes screen just goes blank, i have to manually switch it on.
laughingT said:
Sounds like Battery health status does not equal healthy. That forces an immediate shutdown, whether due to temperature or excessive internal resistance. That's because once a Li ion battery reaches critical temperature, it combusts and destroys your phone, burns you and anything around it, etc.
GET ANOTHER BATTERY ASAP.
Stop trying to circumvent high temperature shut down..........
Click to expand...
Click to collapse
I bought a new battery & it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high".
But im not able to under stand, why is Cynogenmod shuts down itself after installation, can i just stop shutting down ?
vivek90 said:
Recently i bought a new battery, original samsung make, it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high". No overclocking here, just used to call, receive & wifi hotspot. Currently i charge battery in a battery charger & use it in phone.
U pointed out something right, sometimes screen just goes blank, i have to manually switch it on.
I bought a new battery & it states the same thing "charging paused for battery durability" sometimes "Charging stopped battery temps high".
But im not able to under stand, why is Cynogenmod shuts down itself after installation, can i just stop shutting down ?
Click to expand...
Click to collapse
I think it's not CM related but hardware related. Does this happen when not using the wifi hotspot too?
I'm thinking your battery is bad (even if new), charger is bad, connection is bad (maybe from water/humidity) or that your usb port is bad. No easy way of finding it other than testing.
BWolf56 said:
I think it's not CM related but hardware related. Does this happen when not using the wifi hotspot too?
I'm thinking your battery is bad (even if new), charger is bad, connection is bad (maybe from water/humidity) or that your usb port is bad. No easy way of finding it other than testing.
Click to expand...
Click to collapse
May be yes, the phone some times just goes blank, i have to manually switch ON. The same battery works well in my frnds phone quite well.
Port dont know, i can copy files no errors even now when i plug it in on stock gingerbread the battery doesnt charge but can copy files as before.
Since the batt works well in other phone, a couple of ideas. Perhaps silly to ask, but just checking:
did you wipe battery stats in cwm after flashing?
did you clean the phone's battery terminals with a bit of alcohol?
what's the battery health,temperature and voltage history look like, if you can get it. you can log it with battery monitor widget or similar app. set to short 1 minute interval for testing.
.........
Hi all,
Hoping I can get some assistance. I've been using a stock 4.04 ICS ROM (kernel LRK) with a rooted Notecore kernel for the better part of a year without any issues.
My problems started a few days ago when I noticed that my battery wasn't lasting as long as it normally does. I turned off the phone and recharged it fully, then reset the battery stats but it didn't alleviate my problems, instead a few hours later while trying to browse some website, I noticed a terrible screen flicker followed by a soft crash (as in the phone turned unresponsive, screen was off for a few minutes and then restored to lock screen on its own) and I noticed that my battery went from 68% to 18%.
I tried using the phone and the same thing happened again, this time the battery showed 5% remaining and soon after the phone turned off completely as if the battery was completely drained. I put it on charge overnight. When I tried turning on the phone, it was stuck at the boot screen and would not finish loading.
Since I was using an emmc erase disabled kernel, I factory wiped/flashed to a stock Jelly Bean ROM and managed to restore my phone for the most part. It was working correctly while I was trying to set things up until I got to linking my google account (I had skipped this during set up)to download my contacts and settings.
The phone crashed (for the lack of a better term) as soon as my contacts and settings were loaded and now is stuck in a boot loop.
Battery shows about 70% charged.
Lithium Flower said:
Hi all,
Hoping I can get some assistance. I've been using a stock 4.04 ICS ROM (kernel LRK) with a rooted Notecore kernel for the better part of a year without any issues.
My problems started a few days ago when I noticed that my battery wasn't lasting as long as it normally does. I turned off the phone and recharged it fully, then reset the battery stats but it didn't alleviate my problems, instead a few hours later while trying to browse some website, I noticed a terrible screen flicker followed by a soft crash (as in the phone turned unresponsive, screen was off for a few minutes and then restored to lock screen on its own) and I noticed that my battery went from 68% to 18%.
I tried using the phone and the same thing happened again, this time the battery showed 5% remaining and soon after the phone turned off completely as if the battery was completely drained. I put it on charge overnight. When I tried turning on the phone, it was stuck at the boot screen and would not finish loading.
Since I was using an emmc erase disabled kernel, I factory wiped/flashed to a stock Jelly Bean ROM and managed to restore my phone for the most part. It was working correctly while I was trying to set things up until I got to linking my google account (I had skipped this during set up)to download my contacts and settings.
The phone crashed (for the lack of a better term) as soon as my contacts and settings were loaded and now is stuck in a boot loop.
Battery shows about 70% charged.
Click to expand...
Click to collapse
Go back to stock GB ROM via PC Odin and then stay off jellybean leaks.
your battery is weak as your note is a year old now.. buy a new one and everthing will be fine don't mess up with your phone
Sent from my GT-N7000 using Tapatalk 2
abhinav quietly brilliant said:
your battery is weak as your note is a year old now.. buy a new one and everthing will be fine don't mess up with your phone
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
But I don't have any problems with my phone and I bought it when it had just been released?
warfareonly said:
But I don't have any problems with my phone and I bought it when it had just been released?
Click to expand...
Click to collapse
usually i think its because of how every person use the charging procedure. if you leave you phone on charge for a long time even when its full.. it reduces the life of battery ... this i have seen on lot of phones..
nokiamodeln91 said:
usually i think its because of how every person use the charging procedure. if you leave you phone on charge for a long time even when its full.. it reduces the life of battery ... this i have seen on lot of phones..
Click to expand...
Click to collapse
I charge it overnight. Daily.
it's easy.. buy a new battery
Sent from my GT-N7000 using Tapatalk 2
warfareonly said:
I charge it overnight. Daily.
Click to expand...
Click to collapse
Oh! lucky you.. already had to change because of that