I am on AOKP B31 without fast charge enabled but seem to have a problem with the phone charging when off. If I plug it into a USB or wall charger, both samsung, the initial battery screen will come on but after the screen turns off it will not turn back on. I left it there for 30 min turned it on and it showed 50% more battery. We all know with a samsung that is not possible. Just want to see if others are having this issue, or a fix.
Thanks in advance.
I am sporadically having this issue as well- Samsung charger, AOKP b31. I will play with it over the weekend and see if I can figure anything out. For the moment I am not seeing this behavior, but initially after flashing I did...
I have not had this issue on any other THS or AOKP build and I have used a lot of them. The last one I was on was milestone 4 and it was fine.
Sent from my AOKP ICS captivate using XDA
Hmm, still doing it. Setting the Min CPU to 200MHz has not helped, as I have seen posted elsewhere. Charging screen turned off at some point, and when I booted up it was at 64% (from 7%). I'm not super worried about it though, seeing as how I flash like crazy and will not be on Build 31 for any length of time. If I get this on other builds or other Roms I will update again.
Edit: Build 32 is out, so I am going to flash and see if that resolves the issue. I am wondering is this is a kernel issue, as the Glitch for Build 31 was the first time I had switched from Glitch version 14 beta 6. Maybe I'll try the Semaphore kernel if the issue remains.
I flashed 32 and it still is the same issue. Also tried the min CPU increase but nothing. Hopefully it will be fixed soon. My concern is that it will continue to charge after 100%.
Sent from my SGH-I897 using XDA
read the first post of AOKP. report bugs where it tells you to. they will not look here, or will they care if they do look here, if you do not follow their instructions for reporting bugs.
look to see if the bug exists, and if it is there, click the STAR to vote for the issue as that page says to do.
I have read the OP but I did not want to flood the bug tracker if it was a problem already found or known. I did not have the 10 posts needed to post in the development section, so I figured start this to see if anyone had an issue. I know how much everyone hates the development thread being diluted with dumb question after question. I did report it on the bug reporter site.
P.S. - Thanks for your essentials mod, makes everything much easier.
Just wonder - will disable fast charge help?
I have not enabled fast charge. I thought that only effects charging when on USB? I could be wrong though.
Sent from my SGH-I897 using XDA
I have been testing with both i897 and i9000 bootloaders. This may be a Glitch kernel issue, as I have flashed Semaphore ICS kernel 1.0.0 and have not seen this. Looks like there is already a bug reported in the AOKP page. Not a huge concern though, I think, because the phone seems to charge nevertheless.
Related
I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Matt262 said:
I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Click to expand...
Click to collapse
+1-I am having the exact same issues with same setup although I do have AutoKiller and it is set to Optimum.
If you havent already try the Brainfunct kernal from this forum. I used to have random lockups and such before I used that..
Jason kiDD said:
If you havent already try the Brainfunct kernal from this forum. I used to have random lockups and such before I used that..
Click to expand...
Click to collapse
Sorry, I should've mentioned that I DID try the BFS kernel (9/28 build) and it was after flashing kernels that I noticed it (mostly coincidence I'm sure) which is why I flashed straight CM6 to rule out the kernel
Funny as you mentioned it my phone rebooted once and then was non-responsive a second time after being untouched.. You must remember that these are RC1 roms and not final so there will be issues with each iteration.. Its the drawback of pushing our phones to the limit..
Jason kiDD said:
Funny as you mentioned it my phone rebooted once and then was non-responsive a second time after being untouched.. You must remember that these are RC1 roms and not final so there will be issues with each iteration.. Its the drawback of pushing our phones to the limit..
Click to expand...
Click to collapse
It happened with the stock .5 RUU ROM with the only modification being AndROOT...I RUU'd it back to .5 this morning and am going to ride it out untarnished to see if the problem replicates again. If so, I believe I will have successfully found it's a problem with the phone itself, and at that point take it to Sprint and see about paying the $35 for an exchange. I would do the OTA updates but if this shows its fixed I don't want to lose the ability to root, and I don't want to have to RUU back to .5 in order TO root. I was really hoping a dev who understands these ROM's better than I could chime in with some thoughts, but I guess I'll just have to keep test and tuning...I definitely appreciate these responses, though, and I'm happy I'm not the only one having this issue (though I'm still not happy it's happening lol)
not trying to be mean but your better off actually posting this in the right section and you might get some better answers. Q&A section is there for a reason.
t12icky0 said:
not trying to be mean but your better off actually posting this in the right section and you might get some better answers. Q&A section is there for a reason.
Click to expand...
Click to collapse
Thanks...I figured sticking it in the Dev section would be more fitting since my first inclination was strictly a software problem, and not too sure how often dev's surf the other threads.
Matt262 said:
Thanks...I figured sticking it in the Dev section would be more fitting since my first inclination was strictly a software problem, and not too sure how often dev's surf the other threads.
Click to expand...
Click to collapse
oh...devs go in there quite a bit. If not them then plenty of people who know the answers are in there.
I have the same issue I've used stock roms cm6 roms and tons of different kernels. I've noticed it moreso when its been asleep for a while it will wake up fine and then a couple minute later it will freeze up and force me to do a battery pull.
t12icky0 said:
oh...devs go in there quite a bit. If not them then plenty of people who know the answers are in there.
Click to expand...
Click to collapse
Gotcha...if you check out my post count I'm a n00b to these boards, but I appreciate you not blasting me like I've seen others have that happen to them (for not searching ,etc)...maybe a mod could move this for me so I don't clutter the boards?
Dono74 said:
I have the same issue I've used stock roms cm6 roms and tons of different kernels. I've noticed it moreso when its been asleep for a while it will wake up fine and then a couple minute later it will freeze up and force me to do a battery pull.
Click to expand...
Click to collapse
Exactly! Now if a resolution can be found...since I posted this in the wrong section, maybe there is a resolution and I just wasn't in the right spot to see it...
Matt262 said:
I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Click to expand...
Click to collapse
Sounds like a garbage collection fail when coming from sleep, try using ondemand cpu governor for the time being.
Otherwise.. don't set your max freq too high, that's usually where lockups stem from.
Decad3nce said:
Sounds like a garbage collection fail when coming from sleep, try using ondemand cpu governor for the time being.
Otherwise.. don't set your max freq too high, that's usually where lockups stem from.
Click to expand...
Click to collapse
Actually when I flashed CM6 last night with no tweaks I didn't even install SetCPU or any kernels...just the one that came with it capped at 691.2...no battery tweak or anything
I think there is a problem in the latest iteration of CM6 but again its not a promised fully stable build.. All I did since then was to flash the battery tweak over stock CM6 and poof problems were gone.. With the 9/22/10 it was the opposite and i had to flash the Brainfunct kernal instead of the battery tweak one..
Jason kiDD said:
I think there is a problem in the latest iteration of CM6 but again its not a promised fully stable build.. All I did since then was to flash the battery tweak over stock CM6 and poof problems were gone.. With the 9/22/10 it was the opposite and i had to flash the Brainfunct kernal instead of the battery tweak one..
Click to expand...
Click to collapse
Still a mystery to me as to why it's happening with more ROM's than just CM6 though...oh well, I'll see how stock .5 unrooted treats me this weekend, and if I have the same problem happen again, I know it's phone related and not to be blamed on a ROM (which I'd like to make clear -- I do NOT blame CM6, Fresh, or NFXHero for my issues. I know the dev's spent a TON of time building everything for us to have something we would otherwise NOT have, and my sole reason for this post is really to find out exactly what is wrong with my phone, not necessarily with a ROM, and most importantly to find out if I'm the only one experiencing these issues)...I do appreciate all the help and responses, and I'm thoroughly impressed with XDA and the responsiveness of everyone
Just in case anyone was interested at all, my phone completely bricked today (stock .5 running all weekend no issues) and the culprit is the touchscreen and all buttons but power stopped working...sprint's overnighting me a replacement so evidently something got too hot at some point or the like...thanks to all for the responses, and to those who had similar issues (not related to the ROM you're running) then keep an eye out for imminent failure lol
Anyone having issues with their Thunderbolt shutting off and the only way to turn it back on is to do a battery pull? I'm rooted running Ginger3DTh3ory 6.2, but it did this also when I was running Bamf 3.0. Any thoughts on how to fix this?
No idea, are you oc'd?
Sent from my TBolt using my f***king thumbs...
Let me describe what mine has done a few times and you tell me if that's what you're talking about. Twice, in the last 2 days, it's just locked up with the screen off. It doesn't respond to power or volume buttons. Only way to get it to work again it to pull that battery.
BUT... the weirdest thing happened the last time. It did it while I was in a call. I could answer with my bluetooth, talk, and hang up with my bluetooth, but the phone wouldn't respond to anything I did to it.
Is this what you're talking about?
Sound like SOD = Sleep of Death. It doesn't happen to much but a pain in the rear...switch Ur govenor from interativex to ondamandx see if that fixes it
Sent from my ADR6400L using XDA App
I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.
adoublearonn said:
I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.
Click to expand...
Click to collapse
the official build's kernel is a piece of crap that is leading to a whole new batch of reboots.
OP, that is usually an issue where your phone is not getting enough voltage. I would do what the other poster suggested and switch your governor. It will give the phone a little more juice so it doesn't do that.
All phones are different when it comes to that stuff.
Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.
Mines running fine. Maybe try reflashing?
jeck77 said:
Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.
Click to expand...
Click to collapse
you have to open terminal emulator (I think its preinstalled on gingertheory, if not there is a free one in the market).
type su (hit enter), it might drop your keyboard, pressing menu will let you reopen it.
type speedtweak.sh
This will open script fusion, there you can change the governor to ondemandx.
Hi all, I'm new to the forum and cannot post in the development area where this question could be addressed. Hoping someone can help or a admin could move it.. I have a sgs2 sgh-i777 at&t. I'm currently running the new ultimatum beta 4, oc to 1.4.. I have been keeping up with the posts and haven't noticed anyone complaining about my issue. Seems the phone runs fine until about 50% battery then it gives me the sod under that range randomly and if left alone long enough like that it starts heating up. Pull the battery and reboot and if its hot the battery is drained if I catch it in time most of the battery Is salvaged. I did full wipe, cache, and dalvik. Tried to reinstall over it also. Checked the new siyah kernal post also and did the reset tweak it discussed in that post.. any help appreciated. I ran beta 3 just fine fyi., thanks, Brandon
Droidmissionary said:
Hi all, I'm new to the forum and cannot post in the development area where this question could be addressed. Hoping someone can help or a admin could move it.. I have a sgs2 sgh-i777 at&t. I'm currently running the new ultimatum beta 4, oc to 1.4.. I have been keeping up with the posts and haven't noticed anyone complaining about my issue. Seems the phone runs fine until about 50% battery then it gives me the sod under that range randomly and if left alone long enough like that it starts heating up. Pull the battery and reboot and if its hot the battery is drained if I catch it in time most of the battery Is salvaged. I did full wipe, cache, and dalvik. Tried to reinstall over it also. Checked the new siyah kernal post also and did the reset tweak it discussed in that post.. any help appreciated. I ran beta 3 just fine fyi., thanks, Brandon
Click to expand...
Click to collapse
Sounds like you already stated your problem. Seems your device doesn't like the OC settings. Not all devices are created equal. Also you could have posted in the devices Q&A forum where it belongs. instead of here.
Thread closed
Since this forum software won't let me post anywhere on the Development thread, I'll post here.
Cyanogenmod Jellybean R_29. I have the common severe battery drain, which shows the screen sucking up %80 of the battery. Battery drains after 2 hours of constant use. I have read that this is a problem with a certain chipset not running correctly that controls the screen (Kernel bug?). I have autorotation turned off, along with most everything else but wifi. but it still drains. AOSPX delivers great battery, but is too early development to be usable every day.
Is there an alternate kernel available that will run with R_29? I cannot seem to find one anywhere.
Inspire 4g.
Sometimes this one works. http://forum.xda-developers.com/showthread.php?t=1931386. JT isn't officially supported though.
bananagranola said:
Sometimes this one works. http://forum.xda-developers.com/showthread.php?t=1931386. JT isn't officially supported though.
Click to expand...
Click to collapse
MUCH appreciated. I will give this a shot in the next couple hours.
Working perfect. Battery is 3x better. Much thanks!
Sent from my Desire HD using xda app-developers app
Hello, I've been with this problem almost a month and I hope that I can find a solution here. In fact, when my phone is off and I want to charge it by plunging it to a charger, normally, the phone will turn on (but not boot into a ROM) and a charging animation (a big battery with green "juice" in it) will appear. However, when I do the same with by GT-N7100 running JellyBam version jellybam_n7100_jb-PAOKP10-4.1.0-20130116 and kernel 3.0.31-CM-g9d7654c [email protected]#1 Wed Jan 16 08:48:47 CET 2013, it stuck at the screen where there's a loading circle "forever". I do not think it is the ROM problem since at that state the phone is not even booting into the ROM. Also, couple of people on this forum advice me to flash another kernel since that seems to be a kernel problem (but I couldn't see why since the kernel that I am currently using comes with the ROM itself, so I think it should work with the hardware itself). Also, I couldn't find a compatible kernel with the version of the ROM as most of theme included RedPill are out of date. I can upgrade the ROM but it has problem with the newest version. So, I just don't feel comfortable to do the flash right now. Any idea? Do you think it's the ROM problem, the kernel problem or just simply the charging animation that doesn't work properly? I been asking this question multiple times and many researches have been made but nothing and no one can give me a satisfactory answer and here's a link: http://forum.xda-developers.com/showpost.php?p=37923172&postcount=706
Dan Law 001 said:
Hello, I've been with this problem almost a month and I hope that I can find a solution here. In fact, when my phone is off and I want to charge it by plunging it to a charger, normally, the phone will turn on (but not boot into a ROM) and a charging animation (a big battery with green "juice" in it) will appear. However, when I do the same with by GT-N7100 running JellyBam version jellybam_n7100_jb-PAOKP10-4.1.0-20130116 and kernel 3.0.31-CM-g9d7654c [email protected]#1 Wed Jan 16 08:48:47 CET 2013, it stuck at the screen where there's a loading circle "forever". I do not think it is the ROM problem since at that state the phone is not even booting into the ROM. Also, couple of people on this forum advice me to flash another kernel since that seems to be a kernel problem (but I couldn't see why since the kernel that I am currently using comes with the ROM itself, so I think it should work with the hardware itself). Also, I couldn't find a compatible kernel with the version of the ROM as most of theme included RedPill are out of date. I can upgrade the ROM but it has problem with the newest version. So, I just don't feel comfortable to do the flash right now. Any idea? Do you think it's the ROM problem, the kernel problem or just simply the charging animation that doesn't work properly? I been asking this question multiple times and many researches have been made but nothing and no one can give me a satisfactory answer and here's a link: http://forum.xda-developers.com/showpost.php?p=37923172&postcount=706
Click to expand...
Click to collapse
Why are you powering off your phone to charge your battery anyway lol and does it really matter asking as its charging anyway its a kernel issue so its not the ROM its the kernel your on
Sent from my SCH-I500 using Tapatalk 2
It does make a difference between charging your phone when your phone is actually on and charging when it's off. In fact, when it's on and even it's set to low CPU level ( let say 200Mhz), when you connect to your charger, there's still activities in the CPU. Imagine if you leave your phone on and charge it overnight, CPU will work for nothing and leaving the phone off and charge it is a good way to charge your battery in the way that give the CPU some rest. You can not stay awake overnight, your phone can't neither...
Sent from my GT-N7100 using xda premium
Dan Law 001 said:
It does make a difference between charging your phone when your phone is actually on and charging when it's off. In fact, when it's on and even it's set to low CPU level ( let say 200Mhz), when you connect to your charger, there's still activities in the CPU. Imagine if you leave your phone on and charge it overnight, CPU will work for nothing and leaving the phone off and charge it is a good way to charge your battery in the way that give the CPU some rest. You can not stay awake overnight, your phone can't neither...
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Ive never turned my phone off and its been 3yrs I've had this phone (galaxy s1) lol I can only imagine what my CPU is thinking lol
Sent from my SCH-I500 using Tapatalk 2
reply
hope you resolve that problem perfectly
Please help
Dan Law 001 said:
Hello, I've been with this problem almost a month and I hope that I can find a solution here. In fact, when my phone is off and I want to charge it by plunging it to a charger, normally, the phone will turn on (but not boot into a ROM) and a charging animation (a big battery with green "juice" in it) will appear. However, when I do the same with by GT-N7100 running JellyBam version jellybam_n7100_jb-PAOKP10-4.1.0-20130116 and kernel 3.0.31-CM-g9d7654c [email protected]#1 Wed Jan 16 08:48:47 CET 2013, it stuck at the screen where there's a loading circle "forever". I do not think it is the ROM problem since at that state the phone is not even booting into the ROM. Also, couple of people on this forum advice me to flash another kernel since that seems to be a kernel problem (but I couldn't see why since the kernel that I am currently using comes with the ROM itself, so I think it should work with the hardware itself). Also, I couldn't find a compatible kernel with the version of the ROM as most of theme included RedPill are out of date. I can upgrade the ROM but it has problem with the newest version. So, I just don't feel comfortable to do the flash right now. Any idea? Do you think it's the ROM problem, the kernel problem or just simply the charging animation that doesn't work properly? I been asking this question multiple times and many researches have been made but nothing and no one can give me a satisfactory answer and here's a link: http://forum.xda-developers.com/showpost.php?p=37923172&postcount=706
Click to expand...
Click to collapse
My friend. I have ten mtk6575 tablet works good but all of them hanging during powered off charge!!! I need a solution.... please help
+1
:good:
rain_vich said:
My friend. I have ten mtk6575 tablet works good but all of them hanging during powered off charge!!! I need a solution.... please help
Click to expand...
Click to collapse
yes guys im too looking for the solution im on note 2 n7100 but some morons are fine with sayn they do not shut there phones how lame it is .... seriously its bug of kernel and ramdisk ...which already been solved by one of dev at s3 CM bases or AOKP on rom liquidsmooth rom ....
SO STOP TELLING PEOPLE NOT SWITCH OFF MOBILE OR IT DOES NOT MATTER ALL USERS ARE DIFFERENT .....:laugh:
respect
Updates
Was a solution to this ever found?
Found the fix here: https://forum.xda-developers.com/showthread.php?t=2293095&page=3